Important: These forums are for discussions between SkyDemon users. They are not routinely monitored by SkyDemon staff so any urgent issues should be sent directly to our Customer Support.

Controlling automated climb/descent profiles


Author
Message
T67M
T67M
Too Much Forum (22K reputation)Too Much Forum (22K reputation)Too Much Forum (22K reputation)Too Much Forum (22K reputation)Too Much Forum (22K reputation)Too Much Forum (22K reputation)Too Much Forum (22K reputation)Too Much Forum (22K reputation)Too Much Forum (22K reputation)
Group: Forum Members
Posts: 206, Visits: 3.2K
I was just trying out a flight from Redhill to LeTouquet to see how well SkyDemon coped with the stepped-climb required to remain clear of controlled airspace, and found that while I could control the climb to some extent, I couldn't get exactly what I expected without adding in a LOT of extra waypoints. The best I managed is shown below:







In particular, notice that the climb from 1400' to 2400' starts before Bough Beech not after it, thus causing the flight to enter CAS. Second, whereas I would like to step-climb (or even better, cruise-climb with SkyDemon suggesting a desired RoC in fpm) to remain just below CAS at all times, the actual profile created keeps me at 2400' all the way to LYD, then makes one long climb all the way up to FL054 (which, interestingly, is shown as 5400' despite the airspace being define as a flight level).



Am I doing something wrong, or is this something that isn't (yet) supported fully by SkyDemon?



Thanks,



T67M
Reply
publicom
p
Too Much Forum (401 reputation)Too Much Forum (401 reputation)Too Much Forum (401 reputation)Too Much Forum (401 reputation)Too Much Forum (401 reputation)Too Much Forum (401 reputation)Too Much Forum (401 reputation)Too Much Forum (401 reputation)Too Much Forum (401 reputation)
Group: Forum Members
Posts: 38, Visits: 116
I would like to come back on this feature.

First of all: SD is great and probably the Program with the best price-value-relation I own. Also it still makes big steps to get even better. The option to use the iOS-App on Silicon Macs is fantastic and no longer to cope with the windows version for planning, is a relief.

Although in my opinion climb and descent planning is neglected. Its as important as route planning, but it seems to doesn't matter.

It should be possible to define a climb or descent rate any specific leg. Not for the whole aircraft and thats it.

Also it would be helpful to see this rates as well as the planed Altitude in Virtual Radar At least if the User enables this Option. In the windows GUI its standard to see at least the Altitude in the info box (Picture 1). In iOS its hidden behind the leg name which I found only by chance, as the icon > for submenu is missing (Picture 2).

For a useful climb and descent planning it's also necessary to define, where the altitude change has to start and/or end (TOC, TOD i. e.). At present this can only be influenced with the two options „Change level before this leg starts“ or „Start changing level when this leg starts“. For this reason it is necessary to set a lot of waypoints, which are not actually waypoints. This again makes it confusing and will create a unnecessary inflated flightplan.

P. S. Uploading Pictures seems not to work.


Edited 2/14/2023 4:15:05 PM by publicom
GO

Merge Selected

Merge into selected topic...



Merge into merge target...



Merge into a specific topic ID...





Reading This Topic

Login

Explore
Messages
Mentions
Search